Avoid using isinstance()
checks with FuncBase
for type narrowing
#13607
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves mypy's understanding of the mypy codebase, and reduces the number of false positives if you run the selfcheck with
--warn-unreachable
.As stated in this docstring here, mypy doesn't understand type narrowing very well if you use an
isinstance()
check withFuncBase
:mypy/mypy/nodes.py
Lines 528 to 536 in 130e1a4
Instead, it tends to view blocks of code beneath an
if isinstance(foo, FuncBase)
guard as unreachable, leading to a lot of false positives if you run the selfcheck with--warn-unreachable
.